Semantic consistency
| Characteristic Name: | Semantic consistency |
| Dimension: | Consistency |
| Description: | Data is semantically consistent |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of semantically inconsistent data reported per thousand records |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Ensure that semantics of data is consistent within/across applications | (1) All orders placed by the customers are called “Sales order” in all tables/databases. (2) Anti-example: Payment type ( Check) Payment Details (Card type, Card number) |
| Maintenance of data dictionary or standard vocabularies of data semantics | (1) Data dictionary provides technical data as well as semantics of data |
Validation Metric:
| How mature is the creation and implementation of the DQ rules to maintain semantic consistency |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| School admin: a student’s date of birth has the same value and format in the school register as that stored within the Student database. | N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
| A company has a color field that only records red, blue, and yellow. A new requirement makes them decide to break each of these colors down to multiple shadings and thus institute a scheme of recording up to 30 different colors, all of which are variations of red, blue, and yellow. None of the old records are updated to the new scheme, as only new records use it. This data- base will have inconsistency of representation of color that crosses a point in time. | J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Data about an object or event in one data store is semantically Equivalent to data about the same object or event in another data store. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| Data is consistent if it doesn’t convey heterogeneity, neither in contents nor in form – anti examples: Order.Payment. Type = ‘Check’; Order. Payment. CreditCard_Nr = 4252… (inconsistency in contents); Order.requested_by: ‘European Central Bank’;Order.delivered_to: ‘ECB’ (inconsistency in form,because in the first case the customer is identified by the full name, while in the second case the customer’s acronym is used). | KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published. |
| The extent of consistency in using the same values (vocabulary control) and elements to convey the same concepts and meanings in an information object. This also includes the extent of semantic consistency among the same or different components of the object. | STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733. |
Business rules compliance
| Characteristic Name: | Business rules compliance |
| Dimension: | Validity |
| Description: | Data should comply with business rules |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of tasks failed or under performed due to lack of data precision |
| The number of complaints received due to lack of data precision |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Identify data related business rules separately (business rules that determines the value of data elements and business rules that get executed depending on the values of data elements) and organise them into a separate executable data rules engine | (1) The system maintains price routines to handle price related data Element :Discount rate A price routine (procedure) can be maintained to calculate the discount rate considering the rules R1:All registered customers get a discount of 6% |
| Implement a stewardship structure for business rules (parallel to stewardship structure for data) and manage the changes to the rules properly | (1) Sales director is responsible for discounts and his approval is needed to change a discount rate. Only the sales manager can change the rules related to discounts. |
| Maintain an error log to identify the problems resulted in the data rules repository where the problematic data records can be identified precisely | (1) Rules engines |
| Continuously monitor the root causes for the errors recorded in the log and take preventive actions by amending the rules, fixing the technical defects in the system etc. | (1) Some trip data is missing for a particular journey in the go card system and as a result an unacceptable journey duration was resulted. New rules were implemented to process such data using a different criteria |
Validation Metric:
| How mature is the creation and implementation of the data related business rules |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| One common example in education is the student school of record. While most students do not change schools during an academic year, many do, especially in urban settings. Thus, the school at which students are tested may not be the school at which they received most of their instruction. Because school-level student achievement measures become increasingly invalid as the number of mobile students increases, many districts will hold schools accountable only for those students who were enrolled for a full academic year. In this case, student achievement measures for a given school lose validity as the percentage of mobile students increases. | J. G. Watson, S. B. Kraemer, and C. A. Thorn, “Data Quality Essentials. Guide to Implementation: Resources for Applied Practice”, August 2009. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Determines the extent to which data is not missing important relationship linkages. For example, the launch date for a new product must be valid and must be the first week of any quarter, since all new products are launched in the first week of each quarter. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| 1) Data values conform to the Specified Business Rules.
2) A derived or calculated data value is Produced Correctly according to a specified Calculation Formula or set of Derivation Rules. |
ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |